AI Prompt Library

Project Management Template
1  Start a chat in ChatGPT, Claude, or Gemini and attach two files from your kit folder: Project_Management_Template_16X9.pptx and Project Management Template Map.txt 2  Copy any prompt below, paste it into the chat, and answer its questions
Built for the SlideStart Project Management Template · 16:9 build, 307 slides (August 2026) · 307 slides mapped with measured word limits · in tools that can run code, deck prompts return the assembled .pptx
Send feedbackopens your mail app — or email team@slidestart.com
Slide 1 of the Project Management Template

One prompt runs the entire build: it interviews you, reads anything you attach, plans the deck from this template's layouts, then writes every slide — and in ChatGPT or Claude, hands back the assembled .pptx.

Project status report
This week's or month's status: health, progress, risks, asks.
8–12 slides · interviews you, plans the deck, writes or assembles every slide
Preview prompt
Build me a project status report using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I m…
Click to copy prompt
Build me a project status report using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time, never a block of questions; read anything I attached first and skip what it already answers. Story questions first, build questions second.
1. What project, and who reads this report — team, sponsor, steering committee, client?
2. Overall health this period — Red, Amber, or Green — and the one-line reason?
3. What was delivered since the last report, and what slipped?
4. Where does the schedule stand against plan — key milestone dates?
5. Budget and resourcing: spend vs plan, any capacity problems?
6. The top risks and issues right now, with owners?
7. Decisions or help you need from this audience?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: headline health (17 or 21) -> what changed since last time -> workstream progress (30 or 31) -> schedule vs plan (Gantt 215/216 or milestones 185) -> budget or KPIs (146–148) -> risks and issues (213, 115, or 98) -> asks and next steps. Status is a claim: every Red/Amber/Green must trace to a fact I gave you. Choose layouts per the map's selection rules, only from its catalog. Show a numbered plan — slide number and layout name | working action title | one line on contents — and ask me to approve or edit before writing anything.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Steering committee update
For the group that owns the decisions: status, exceptions, and the choices they must make.
10–14 slides · decision-first structure
Preview prompt
Build me a steering committee update using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else.…
Click to copy prompt
Build me a steering committee update using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time; read anything I attached first and skip what it already answers.
1. What program or project, and who sits on the steering committee?
2. What decisions does this meeting need to produce? (This shapes everything.)
3. Overall status and trajectory since the last meeting — better, worse, stable?
4. The exceptions: what's off plan, by how much, and why?
5. Options you're bringing for each decision, with your recommendation?
6. Money and dates: current spend vs budget, current forecast vs baseline?
7. Risks the committee should own or escalate?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Steering committees decide; they don't tour the project. Arc: executive scorecard up front (212 or 21) -> exceptions only, worst first -> each decision as its own slide with options (66 or 179) and a recommendation -> schedule reality (216 planned vs actual) -> risk position (213) -> the asks, dated. Everything else goes to appendix. Choose layouts per the map's selection rules. Show a numbered plan and ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Project kickoff deck
Objectives, scope, plan, team, and ways of working — the deck that starts the project.
12–18 slides · aligns the team and the sponsor on day one
Preview prompt
Build me a project kickoff deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I ma…
Click to copy prompt
Build me a project kickoff deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time; read anything I attached first and skip what it already answers.
1. What's the project, and why now — the problem or opportunity behind it?
2. Who's in the room at kickoff, and what must they leave aligned on?
3. Objectives and success criteria — how will you know it worked?
4. Scope: what's in, and just as important, what's explicitly out?
5. The plan: phases, key milestones, target dates?
6. The team: roles, owners, and who decides what?
7. Ways of working: cadence, tools, escalation path?
8. Known risks going in?
Finish with three build questions: how many slides (suggest 12–18); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: why this project exists (144 problem statement or 13) -> objectives (133/134 or SMART 116) -> scope in/out (90 or 66) -> the plan (roadmap 188–205, then Gantt 215–222 if dates are firm) -> team and RACI (228–233, 113/114) -> ways of working (76 or 143) -> risks going in (115) -> next 30 days and asks. Choose layouts per the map's selection rules. Show a numbered plan and ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Project plan & roadmap
The plan itself: phases, milestones, dependencies, owners, and dates.
10–16 slides · the schedule is the star
Preview prompt
Build me a project plan and roadmap deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything e…
Click to copy prompt
Build me a project plan and roadmap deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time; read anything I attached first and skip what it already answers.
1. What project, and who needs to approve or work from this plan?
2. The phases or waves, with your names for them?
3. Key milestones and their dates — and which dates are commitments vs estimates?
4. Workstreams and their owners?
5. Dependencies: what blocks what, and what do you depend on outside the team?
6. Resourcing: who's on this and at what capacity?
7. What could move the dates — the risks to the plan itself?
Finish with three build questions: how many slides (suggest 10–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the plan on a page (roadmap 192/194 or milestones 185) -> phase detail (chevron table 105 or per-phase chevrons 51–54) -> the master schedule (Gantt 215–222; sprint plans 224/225 for agile cadence) -> dependencies (PERT 119–121 or flowchart 235) -> owners (WBS 232 or RACI 113) -> capacity (207/208) -> plan risks -> what happens next. Every date must agree across timeline, Gantt, and text — the map's preflight will check. Show a numbered plan and ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Project charter presentation
The charter as a deck: purpose, scope, success criteria, governance, and sign-off.
8–12 slides · turns the charter document into an approval meeting
Preview prompt
Build me a project charter presentation using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything el…
Click to copy prompt
Build me a project charter presentation using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time; read anything I attached first and skip what it already answers. If I attach a charter document, mine it first.
1. The project, its sponsor, and who approves this charter?
2. The business need — what problem, what cost of doing nothing?
3. Objectives and measurable success criteria?
4. Scope boundaries: in, out, and the gray areas that caused debate?
5. High-level timeline and budget envelope?
6. Governance: who decides, who's consulted, escalation path?
7. Constraints and assumptions worth stating out loud?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: why this project (144) -> the charter on a page (142 or 143 — six sections: purpose, scope, success, timeline, team, budget) -> objectives (116 SMART or 133) -> scope (90 do's/don'ts as in/out) -> timeline envelope (184/185) -> governance and RACI (113/114) -> assumptions and risks (115) -> the sign-off ask. Show a numbered plan and ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Business case / project proposal
The case for doing the project: problem, options, recommendation, cost, return, plan.
12–18 slides · built to win an approval
Preview prompt
Build me a business case presentation using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else…
Click to copy prompt
Build me a business case presentation using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time; read anything I attached first and skip what it already answers.
1. What are you proposing, and who approves it?
2. The problem: what's broken or what opportunity is being missed, with numbers?
3. What does doing nothing cost?
4. The options you considered — including the ones you rejected, and why?
5. Your recommendation and its price: investment, timeline, team?
6. The return: benefits, when they land, and how you'll measure them?
7. Key risks of proceeding, and your mitigations?
Finish with three build questions: how many slides (suggest 12–18); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the problem, priced (144 with stat cards) -> cost of doing nothing -> options fairly compared (66, 155/156, or 179) -> the recommendation -> the plan (roadmap then Gantt) -> investment and return (17 stat cards; chart 249/262 for the trajectory) -> risks and mitigations (213 or 98) -> the ask with dates. Every option must be one a reasonable person could pick — no straw men. Show a numbered plan and ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Risk & issue review
A working session on the risk register: position, movement, hot items, decisions.
8–12 slides · turns the register into a conversation
Preview prompt
Build me a risk and issue review deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else…
Click to copy prompt
Build me a risk and issue review deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time; read anything I attached first and skip what it already answers. If I attach a risk register, mine it first.
1. What project or program, and who's in the review?
2. The risk position overall: how many open, how has it moved since last review?
3. The top risks by exposure — probability, impact, owner, mitigation status?
4. Live issues (things that already happened) and their recovery plans?
5. Assumptions and dependencies worth re-testing?
6. Any risks that need escalation or a decision today?
Finish with three build questions: how many slides (suggest 8–12); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: position at a glance (213 heat matrix) -> movement since last review -> the RAID log (115) -> hot risks one by one, worst first, each with owner and a mitigation that names a mechanism -> issues and recoveries (98 activity table) -> escalations and decisions -> agreed actions with owners and dates. Every rating must trace to a stated fact — never assign a severity I didn't give you. Show a numbered plan and ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Quarterly program review
The quarter in review: results vs plan, health across projects, lessons, next quarter.
12–16 slides · the portfolio-level look back and forward
Preview prompt
Build me a quarterly program review deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything e…
Click to copy prompt
Build me a quarterly program review deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time; read anything I attached first and skip what it already answers.
1. What program or portfolio, and who's in the review?
2. The quarter's plan vs what actually happened — the honest deltas?
3. Health by project or workstream right now?
4. The KPIs that matter, with current vs target?
5. What the quarter taught you — what you'd do differently?
6. Next quarter's priorities and milestones?
7. Asks: budget, people, decisions?
Finish with three build questions: how many slides (suggest 12–16); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the quarter's headline (17 or 20) -> results vs plan -> health across the portfolio (299/300 multi-project, or 210/211 RAG cards) -> KPI scorecard (146–148 or dashboard 301/302) -> deep-dives on the exceptions only -> lessons learned -> next quarter's plan (192 or 224) -> asks. Show a numbered plan and ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Agile sprint review
Sprint outcomes, velocity, demo highlights, blockers, and the next sprint's plan.
6–10 slides · for the sprint review or PI ceremony
Preview prompt
Build me a sprint review deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may …
Click to copy prompt
Build me a sprint review deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time; read anything I attached first and skip what it already answers.
1. What team and which sprint (or PI), and who attends the review?
2. Sprint goal — met, partially met, or missed, and why?
3. What shipped: the stories or features done, and any demo highlights?
4. Velocity and carry-over: planned vs completed points?
5. Blockers hit, and which remain?
6. Next sprint's goal and committed scope?
Finish with three build questions: how many slides (suggest 6–10); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: sprint goal verdict up front -> what shipped (23/24 cards or 27 icon grid) -> velocity (chart 251 or stat cards 17) -> blockers and impediments -> the sprint roadmap in context (224 releases×sprints, or 225 workstreams×sprints) -> next sprint's commitment. Keep it lean — sprint reviews die of ceremony. Show a numbered plan and ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Project closeout & lessons learned
The final report: what was delivered, against what plan, at what cost, and what to keep.
10–14 slides · closes the project properly
Preview prompt
Build me a project closeout deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I m…
Click to copy prompt
Build me a project closeout deck using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time; read anything I attached first and skip what it already answers.
1. What project, and who receives the closeout — sponsor, PMO, client?
2. What was delivered vs the original scope — including what was descoped and why?
3. Final schedule vs baseline: where did time go?
4. Final cost vs budget?
5. The results so far: benefits realized or on track?
6. Lessons: what worked, what didn't, what the next project should steal or avoid?
7. Open items being handed over, with owners?
Finish with three build questions: how many slides (suggest 10–14); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: the verdict up front (17 stat cards: delivered, schedule, cost, benefits) -> scope delivered vs planned (90 or 137 before→after) -> schedule story (216 planned vs actual Gantt) -> cost story -> benefits and KPIs -> lessons learned (58/59 worked vs didn't, or sticky notes 71/72 from the retro) -> handover items (98 owner/date table) -> thanks and formal close (305–307). Honest deltas beat victory laps — the audience knows what happened. Show a numbered plan and ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Executive dashboard readout
The portfolio on a page: health, KPIs, spend, and the exceptions that need attention.
5–8 slides · maximum signal, minimum ceremony
Preview prompt
Build me an executive dashboard readout using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything el…
Click to copy prompt
Build me an executive dashboard readout using my SlideStart Project Management Template.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — INTERVIEW ME. One question at a time; read anything I attached first and skip what it already answers.
1. What portfolio or program, and which executive audience?
2. The projects or workstreams on the dashboard, each with current RAG status and the fact behind it?
3. The 4–6 KPIs that steer this portfolio, current vs target?
4. Spend position vs budget?
5. The exceptions — what needs executive attention or a decision this cycle?
Finish with three build questions: how many slides (suggest 5–8); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Arc: everything on one dashboard (297/298, or 301/302 with charts) -> multi-project status (299/300) -> the KPI detail only where a number is off (146–148) -> spend (17 or chart 250) -> exceptions and asks. Five slides that get read beat fifteen that get skimmed. Every RAG must trace to a fact. Show a numbered plan and ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.
Turn my plan or tracker into a deck
Attach a project plan, tracker, or spreadsheet — get a deck built around what's in it.
reads your file first · plans the deck from your actual data
Preview prompt
Turn my attached project file into a presentation using my SlideStart Project Management Template. I'm attaching my plan, tracker, status export, or spreadsheet alongside the map.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing r…
Click to copy prompt
Turn my attached project file into a presentation using my SlideStart Project Management Template. I'm attaching my plan, tracker, status export, or spreadsheet alongside the map.

I've attached "Project Management Template Map.txt" — read it first; it has every mapped layout, each slide's exact content slots and measured word limits, the selection rules, and the writing rules. Follow it throughout. If it isn't attached, stop and ask me for it before anything else. I may also have attached the template's .pptx and my own data or documents.

STEP 1 — READ MY FILE, THEN INTERVIEW ME. Mine the attachment first: milestones, dates, owners, statuses, numbers. Then ask only what the file doesn't answer, one question at a time: who the deck is for, the decision or update it serves, what's changed recently that the file may not show, and anything in the file that's stale. Finish with three build questions: how many slides (suggest a count based on what the file supports); is anything confidential (if yes, use the map's sensitive mode); and — if you'll assemble the file — delete the unplanned template slides or keep the full library in the file? Deleting is destructive: confirm before doing it.

STEP 2 — PROPOSE THE PLAN. Map my data to layouts per the map's selection rules: milestone lists -> timelines or Gantt (185, 215–222); status columns -> RAG cards (210/211) or progress bars (30/31); numeric columns -> stat cards (17, 146–148) or chart slides (247–264) with the exact data table to paste; owner columns -> RACI (113) or the activity table (98). Show a numbered plan with, per slide, which rows or columns of my file feed it. Never propose an exhibit the data can't support. Ask me to approve before writing.

STEP 3 — BUILD. If you can run code on the attached template file, assemble the deck per the map's ASSEMBLY section and give me the finished .pptx plus the preflight lists. Otherwise, write one slide per message as labeled slots per the map's spec, and end with the preflight.